According to the self-reported version in its response header, the version of nginx hosted on the remote web server is less than 1.8.1 or 1.9.x prior to 1.9.10. It is, therefore, affected by multiple vulnerabilities as noted in the vendor advisory.

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

It was discovered that there was a invalid pointer deference in nginx, a small, powerful, scalable web/proxy server. An invalid pointer dereference might occur during DNS server response processing, allowing an attacker who is able to forge UDP packets from the DNS server to cause worker process crash

For Debian 6 Squeeze, this issue has been fixed in nginx version 0.7.67-3+squeeze4+deb6u1.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Maxim Dounin reports :

Several problems in nginx resolver were identified, which might allow an attacker to cause worker process crash, or might have potential other impact if the 'resolver' directive is used in a configuration file.

According to the self-reported version in its response header, the version of nginx hosted on the remote web server is less than 1.8.1 or 1.9.x prior to 1.9.10. It is, therefore, affected by multiple vulnerabilities as noted in the vendor advisory.

This update to nginx 1.8.1 fixes the following issues :

  - CVE-2016-0742: Invalid pointer dereference during DNS     server response processing (boo#963781)

  - CVE-2016-0746: Use-after-free condition during CNAME     response processing (boo#963778)

  - CVE-2016-0747: Resource exhaustion through unlimited     CNAME resolution (boo#963775)

It was discovered that nginx incorrectly handled certain DNS server responses when the resolver is enabled. A remote attacker could possibly use this issue to cause nginx to crash, resulting in a denial of service. (CVE-2016-0742)

It was discovered that nginx incorrectly handled CNAME response processing when the resolver is enabled. A remote attacker could use this issue to cause nginx to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2016-0746)

It was discovered that nginx incorrectly handled CNAME resolution when the resolver is enabled. A remote attacker could possibly use this issue to cause nginx to consume resources, resulting in a denial of service. (CVE-2016-0747).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-201606-06 (nginx: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in nginx. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker could possibly cause a Denial of Service condition via       a crafted packet.
  Workaround :

    There is no known workaround at this time.

Several vulnerabilities were discovered in the resolver in nginx, a small, powerful, scalable web/proxy server, leading to denial of service or, potentially, to arbitrary code execution. These only affect nginx if the 'resolver' directive is used in a configuration file.

It was discovered that nginx could perform an out of bound read and dereference an invalid pointer when resolving CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to crash if nginx enabled the resolver in its configuration. (CVE-2016-0742)

A use-after-free flaw was found in the way nginx resolved certain CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to crash or, possibly, execute arbitrary code if nginx enabled the resolver in its configuration. (CVE-2016-0746)

It was discovered that nginx did not limit recursion when resolving CNAME DNS records. An attacker able to manipulate DNS responses received by nginx could use this flaw to cause a worker process to use an excessive amount of resources if nginx enabled the resolver in its configuration. (CVE-2016-0747)

ID	Name	Product	Family	Published	Updated	Severity
98963	Nginx < 1.8.1 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	11/5/2018	3/14/2023	critical
98962	Nginx < 1.9.10 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	11/5/2018	3/14/2023	critical
88422	Debian DLA-404-1 : nginx security update	Nessus	Debian Local Security Checks	1/28/2016	1/11/2021	medium
88503	FreeBSD : nginx -- multiple vulnerabilities (c1c18ee1-c711-11e5-96d6-14dae9d210b8)	Nessus	FreeBSD Local Security Checks	2/1/2016	1/4/2021	high
107265	nginx < 1.8.1 / 1.9.x < 1.9.10 Multiple Vulnerabilities	Nessus	Web Servers	3/9/2018	4/11/2022	high
88614	openSUSE Security Update : nginx (openSUSE-2016-161)	Nessus	SuSE Local Security Checks	2/8/2016	1/19/2021	high
88678	Ubuntu 14.04 LTS : nginx vulnerabilities (USN-2892-1)	Nessus	Ubuntu Local Security Checks	2/10/2016	10/20/2023	critical
103587	GLSA-201606-06 : nginx: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	10/2/2017	1/11/2021	high
88702	Debian DSA-3473-1 : nginx - security update	Nessus	Debian Local Security Checks	2/12/2016	1/11/2021	high
89120	Amazon Linux AMI : nginx (ALAS-2016-655)	Nessus	Amazon Linux Local Security Checks	3/4/2016	4/18/2018	high

Detections

Analytics

Plugins Search

critical

critical

medium

high

high

high

critical

high

high

high